Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46e9f42915c2bf10a99e6fab911c2643d3aa3a665bcef3ccea7b7e6181a198f4

Tx prefix hash: f28eac2f60b7c8ac60061364b9b7c70aa167c96257fce601c683e9616f437d78
Tx public key: 590071c414c4cda1b0814f9a0c3d076d04467e42d86f968e5ff8a70bf8af758f
Timestamp: 1742990650 Timestamp [UCT]: 2025-03-26 12:04:10 Age [y:d:h:m:s]: 00:310:16:56:37
Block: 1247663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219721 RingCT/type: yes/0
Extra: 01590071c414c4cda1b0814f9a0c3d076d04467e42d86f968e5ff8a70bf8af758f02110000000fd2e40efd000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c177dd3cbcbc61d8612a6694b5533ca02556241b5478d75f4a68d35c94767d84 0.600000000000 1734690 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": 1247673, "vin": [ { "gen": { "height": 1247663 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c177dd3cbcbc61d8612a6694b5533ca02556241b5478d75f4a68d35c94767d84" } } ], "extra": [ 1, 89, 0, 113, 196, 20, 196, 205, 161, 176, 129, 79, 154, 12, 61, 7, 109, 4, 70, 126, 66, 216, 111, 150, 142, 95, 248, 167, 11, 248, 175, 117, 143, 2, 17, 0, 0, 0, 15, 210, 228, 14, 253, 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