Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b3441b01a2e51ef6b42012792476a280df635ac0f4ad975287a3147ca8a6b92d

Tx prefix hash: 1621cefbbf163a0cb1db6748ed251084314a7967ac85c2df9f51a50d94580a1f
Tx public key: 66e1d04e9b7cd8ed89637378764325bd9a4b1185429b3d260c1f34b829a7180e
Timestamp: 1726261269 Timestamp [UCT]: 2024-09-13 21:01:09 Age [y:d:h:m:s]: 01:056:09:41:34
Block: 1109458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298734 RingCT/type: yes/0
Extra: 0166e1d04e9b7cd8ed89637378764325bd9a4b1185429b3d260c1f34b829a7180e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39b26778851c035d1ab04165b93edeb35133de4a901940a63b2156fe4b2a6c0c 0.600000000000 1587721 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1109468, "vin": [ { "gen": { "height": 1109458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39b26778851c035d1ab04165b93edeb35133de4a901940a63b2156fe4b2a6c0c" } } ], "extra": [ 1, 102, 225, 208, 78, 155, 124, 216, 237, 137, 99, 115, 120, 118, 67, 37, 189, 154, 75, 17, 133, 66, 155, 61, 38, 12, 31, 52, 184, 41, 167, 24, 14, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8