Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c608b6a52a2f8ab0c9260358420436bb2a652fa07b62a58646b8e78c0583435

Tx prefix hash: c8f3c7fd4d99f396f61ec6d7ae9cf4b09f26f10e0408d5a33886c91184dec20e
Tx public key: 4305133550067c1f0b6830e6f9469dc448e748c029362cb78bb4e5b467627f5a
Timestamp: 1718580515 Timestamp [UCT]: 2024-06-16 23:28:35 Age [y:d:h:m:s]: 00:281:05:10:13
Block: 1045803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200927 RingCT/type: yes/0
Extra: 014305133550067c1f0b6830e6f9469dc448e748c029362cb78bb4e5b467627f5a0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47321b8f99f4cf220b686bb33115e945ebc6b004c493196cafb837fe8d4147c0 0.600000000000 1515478 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": 1045813, "vin": [ { "gen": { "height": 1045803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47321b8f99f4cf220b686bb33115e945ebc6b004c493196cafb837fe8d4147c0" } } ], "extra": [ 1, 67, 5, 19, 53, 80, 6, 124, 31, 11, 104, 48, 230, 249, 70, 157, 196, 72, 231, 72, 192, 41, 54, 44, 183, 139, 180, 229, 180, 103, 98, 127, 90, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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