Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e60382ce56e45d7d4e4b7e9b70b95a4f1526c6a5790408ff69eccfd2d2b9fe89

Tx prefix hash: e013a2a041dbba1af2bf7cd8b09ec6c2da90b77d19328004950105d1d32fd07f
Tx public key: 63ec0c6ee9a9a52007fa73f4db841fc85c108c994a7289ec24f627fe5a53780c
Timestamp: 1740256469 Timestamp [UCT]: 2025-02-22 20:34:29 Age [y:d:h:m:s]: 00:271:01:15:49
Block: 1225020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191492 RingCT/type: yes/0
Extra: 0163ec0c6ee9a9a52007fa73f4db841fc85c108c994a7289ec24f627fe5a53780c021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48a62b7bee372eb0cca8cc6c932fea9eda27892f7987e5a3430219b854db0704 0.600000000000 1711885 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": 1225030, "vin": [ { "gen": { "height": 1225020 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48a62b7bee372eb0cca8cc6c932fea9eda27892f7987e5a3430219b854db0704" } } ], "extra": [ 1, 99, 236, 12, 110, 233, 169, 165, 32, 7, 250, 115, 244, 219, 132, 31, 200, 92, 16, 140, 153, 74, 114, 137, 236, 36, 246, 39, 254, 90, 83, 120, 12, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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