Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d2338f589da2419bbfdcf4845cefd3d83ee2e34fa2e16bd78bd5e66d99e514f

Tx prefix hash: a612619f07b3a19091799185e7141ef7a6ca98600bdb59e9ea78c3a1df0b76d3
Tx public key: e9eccc12d57c8079e1118cc551e9267aee8b1c89c8aa633a8c9446f06e1214d9
Timestamp: 1754383106 Timestamp [UCT]: 2025-08-05 08:38:26 Age [y:d:h:m:s]: 00:020:11:33:57
Block: 1340668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13687 RingCT/type: yes/0
Extra: 01e9eccc12d57c8079e1118cc551e9267aee8b1c89c8aa633a8c9446f06e1214d9021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 055952cd28a17140d3016f5696b8e8b9616c446460ac1d0ca9de427b4557924c 0.600000000000 1828487 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": 1340678, "vin": [ { "gen": { "height": 1340668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "055952cd28a17140d3016f5696b8e8b9616c446460ac1d0ca9de427b4557924c" } } ], "extra": [ 1, 233, 236, 204, 18, 213, 124, 128, 121, 225, 17, 140, 197, 81, 233, 38, 122, 238, 139, 28, 137, 200, 170, 99, 58, 140, 148, 70, 240, 110, 18, 20, 217, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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