Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d57b96f8693a928d323221ef454d3099833a1d399ed99bac13b78ec241cc311

Tx prefix hash: 4997376471d0d5463a628617d87636c1d6a3c14b3ff5f8870cab5de2e3e90321
Tx public key: 560ef8afc750bced10d2fb8198db2092d8e53c89181a06021a6251de5a5e273f
Timestamp: 1702627397 Timestamp [UCT]: 2023-12-15 08:03:17 Age [y:d:h:m:s]: 01:332:04:43:15
Block: 913520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496284 RingCT/type: yes/0
Extra: 01560ef8afc750bced10d2fb8198db2092d8e53c89181a06021a6251de5a5e273f02110000000a33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a1d8bd3b49232e9afbb1cb5a7ab152dabb7bbe294d3fe351f07617e5b932d86 0.600000000000 1370792 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": 913530, "vin": [ { "gen": { "height": 913520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a1d8bd3b49232e9afbb1cb5a7ab152dabb7bbe294d3fe351f07617e5b932d86" } } ], "extra": [ 1, 86, 14, 248, 175, 199, 80, 188, 237, 16, 210, 251, 129, 152, 219, 32, 146, 216, 229, 60, 137, 24, 26, 6, 2, 26, 98, 81, 222, 90, 94, 39, 63, 2, 17, 0, 0, 0, 10, 51, 175, 153, 244, 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