Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a122a512d93f9314edff842b5318389870fbf837c785eb69b55d60ae1d2b357

Tx prefix hash: cf32db79fe72eec188bf7fe777e2d4896da58a40d8888c6810d97f1dc1aa853d
Tx public key: a3e7e2dc9bc435b861413048e5017910a20d3aac9cdb3fff1bcd0e4c9c4f3eb2
Timestamp: 1750932568 Timestamp [UCT]: 2025-06-26 10:09:28 Age [y:d:h:m:s]: 00:141:03:31:23
Block: 1313107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98872 RingCT/type: yes/0
Extra: 01a3e7e2dc9bc435b861413048e5017910a20d3aac9cdb3fff1bcd0e4c9c4f3eb202110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91596b78a461131bd526f1efee5496b9cfc591198f07c8899646b9fffe690914 0.600000000000 1800744 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": 1313117, "vin": [ { "gen": { "height": 1313107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91596b78a461131bd526f1efee5496b9cfc591198f07c8899646b9fffe690914" } } ], "extra": [ 1, 163, 231, 226, 220, 155, 196, 53, 184, 97, 65, 48, 72, 229, 1, 121, 16, 162, 13, 58, 172, 156, 219, 63, 255, 27, 205, 14, 76, 156, 79, 62, 178, 2, 17, 0, 0, 0, 1, 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