Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed762c00ed9e22a7506ff58ed300ebdb8d9fba4ca1c0208c4051fe4748c6012a

Tx prefix hash: 807f7be20f51509db4dfab0f857549cf592211fecb29d69f5a8a5252f1579121
Tx public key: 8efb642311cfd7d0522d01e4331eb2c1b781786448010c2d5b4cf9c0fc88e7b2
Timestamp: 1720170202 Timestamp [UCT]: 2024-07-05 09:03:22 Age [y:d:h:m:s]: 00:282:07:26:43
Block: 1058960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201732 RingCT/type: yes/0
Extra: 018efb642311cfd7d0522d01e4331eb2c1b781786448010c2d5b4cf9c0fc88e7b20211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a42f235d85c6495cad19de8fc8af8c5b9e31b2da3ae4bd050de379ff4fe3a13b 0.600000000000 1529419 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": 1058970, "vin": [ { "gen": { "height": 1058960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a42f235d85c6495cad19de8fc8af8c5b9e31b2da3ae4bd050de379ff4fe3a13b" } } ], "extra": [ 1, 142, 251, 100, 35, 17, 207, 215, 208, 82, 45, 1, 228, 51, 30, 178, 193, 183, 129, 120, 100, 72, 1, 12, 45, 91, 76, 249, 192, 252, 136, 231, 178, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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