Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e8f2acdeeb8a2439dcc007cbe446923f05806b9b2b773e31db970df885b92c2

Tx prefix hash: c3fc1e3e3424c3d5b2726fc0d4d0e74eb29ac071c15df3c0b3d8fee1ee36d13f
Tx public key: 3873700e1eedbeb8d77d4e012fc9584dccf2f0100de1bbe4d779d2dc45e2f0a3
Timestamp: 1684989839 Timestamp [UCT]: 2023-05-25 04:43:59 Age [y:d:h:m:s]: 01:191:23:52:04
Block: 767561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398620 RingCT/type: yes/0
Extra: 013873700e1eedbeb8d77d4e012fc9584dccf2f0100de1bbe4d779d2dc45e2f0a302110000000275e3f0e9000000000000000000

1 output(s) for total of 1.756919871000 dcy

stealth address amount amount idx
00: 61e5bf0643fe924856ccbd4a3b3adba80029278d616e4c54238da71f10292e79 1.756919871000 1216686 of 0

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": 767571, "vin": [ { "gen": { "height": 767561 } } ], "vout": [ { "amount": 1756919871, "target": { "key": "61e5bf0643fe924856ccbd4a3b3adba80029278d616e4c54238da71f10292e79" } } ], "extra": [ 1, 56, 115, 112, 14, 30, 237, 190, 184, 215, 125, 78, 1, 47, 201, 88, 77, 204, 242, 240, 16, 13, 225, 187, 228, 215, 121, 210, 220, 69, 226, 240, 163, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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