Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ee55d1610e66055bfb6351845ce768bcaafedcbae62f74a0306a779a7d8829b

Tx prefix hash: 01c40a151cc3648f1a08de50bd6ca29f2f49962f23d0491a4bd90b0cf84eaec4
Tx public key: 316dad51f1d1630ce9d3e9dabcc32a33b57423f14f0f9e0cbff0b38e26075d15
Timestamp: 1734031939 Timestamp [UCT]: 2024-12-12 19:32:19 Age [y:d:h:m:s]: 00:096:22:32:55
Block: 1173803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69062 RingCT/type: yes/0
Extra: 01316dad51f1d1630ce9d3e9dabcc32a33b57423f14f0f9e0cbff0b38e26075d15021100000001a2d75f44000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e871b8a5bfd6cd3c1bff6d19a4d10885424fc74541478d687b2dd7eda2e9aa3e 0.600000000000 1659868 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": 1173813, "vin": [ { "gen": { "height": 1173803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e871b8a5bfd6cd3c1bff6d19a4d10885424fc74541478d687b2dd7eda2e9aa3e" } } ], "extra": [ 1, 49, 109, 173, 81, 241, 209, 99, 12, 233, 211, 233, 218, 188, 195, 42, 51, 181, 116, 35, 241, 79, 15, 158, 12, 191, 240, 179, 142, 38, 7, 93, 21, 2, 17, 0, 0, 0, 1, 162, 215, 95, 68, 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