Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2876cdf5a4fbd8dde8961efbf291dc8191a66995e9a91f417123003f32dac144

Tx prefix hash: 5006af261090ce065e92c8fcc160907b654dce246a940f588e4ea2e50734850e
Tx public key: 5da8462f4bcd964dc30f253a293e201ecc48e8d81946ff25d4b6e2f7c76ae29a
Timestamp: 1751002092 Timestamp [UCT]: 2025-06-27 05:28:12 Age [y:d:h:m:s]: 00:146:16:51:47
Block: 1313661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102868 RingCT/type: yes/0
Extra: 015da8462f4bcd964dc30f253a293e201ecc48e8d81946ff25d4b6e2f7c76ae29a02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 198a1beac39475513d2ecfa16bb33518c2f645b158ee6ce05d67f3a412a70e45 0.600000000000 1801302 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": 1313671, "vin": [ { "gen": { "height": 1313661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "198a1beac39475513d2ecfa16bb33518c2f645b158ee6ce05d67f3a412a70e45" } } ], "extra": [ 1, 93, 168, 70, 47, 75, 205, 150, 77, 195, 15, 37, 58, 41, 62, 32, 30, 204, 72, 232, 216, 25, 70, 255, 37, 212, 182, 226, 247, 199, 106, 226, 154, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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