Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c949a6189724be73715a2c14920ebfa1d7e0a9c5b09b1e4a069e872b5f87a9f7

Tx prefix hash: 2a513742baee7bc8648636c157d6af9856f16f39033e89a40be645db57af4dde
Tx public key: 402a82a662bff90c80292939d05b10a18ccc1af9a12485b499335c5f68d19d85
Timestamp: 1754842487 Timestamp [UCT]: 2025-08-10 16:14:47 Age [y:d:h:m:s]: 00:109:16:15:53
Block: 1344254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77591 RingCT/type: yes/0
Extra: 01402a82a662bff90c80292939d05b10a18ccc1af9a12485b499335c5f68d19d85021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac7160e79d3b1d419a3c0e40791cdc7b05e5ec5a2af31c10079902efd305c552 0.600000000000 1832135 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": 1344264, "vin": [ { "gen": { "height": 1344254 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac7160e79d3b1d419a3c0e40791cdc7b05e5ec5a2af31c10079902efd305c552" } } ], "extra": [ 1, 64, 42, 130, 166, 98, 191, 249, 12, 128, 41, 41, 57, 208, 91, 16, 161, 140, 204, 26, 249, 161, 36, 133, 180, 153, 51, 92, 95, 104, 209, 157, 133, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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