Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08ef66fcf2d0b8d843f3d0d7d96fbc52ace6e873d0fa0ee94c9168b2b0215036

Tx prefix hash: d79a87e970a02ff637c906e3cb354260863ec173d72b0b7c969dccf994e714c1
Tx public key: 039f7447f069097dfc911366ecddd3cd158b6355fc2b74a3f5bfd77cb8401bfd
Timestamp: 1721473128 Timestamp [UCT]: 2024-07-20 10:58:48 Age [y:d:h:m:s]: 00:173:14:26:42
Block: 1069771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124212 RingCT/type: yes/0
Extra: 01039f7447f069097dfc911366ecddd3cd158b6355fc2b74a3f5bfd77cb8401bfd021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03672dc5f558d15320d2e8efcc2b6899399f456bb19e1b6f1422106f963bc2be 0.600000000000 1541332 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": 1069781, "vin": [ { "gen": { "height": 1069771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03672dc5f558d15320d2e8efcc2b6899399f456bb19e1b6f1422106f963bc2be" } } ], "extra": [ 1, 3, 159, 116, 71, 240, 105, 9, 125, 252, 145, 19, 102, 236, 221, 211, 205, 21, 139, 99, 85, 252, 43, 116, 163, 245, 191, 215, 124, 184, 64, 27, 253, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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