Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd5e4f8e5ba6ef4926860b787cbbfb5350f22e74bb1f8ede3f4bc2f3913cf783

Tx prefix hash: cd0cc5ddeda1f6f649c5b4d12b666168e60fe556c18efc937abe83f704eee6d4
Tx public key: 649162e2dbef72cc15869826816af640ec0ec5fcce4649d3a27b11f7a6b73e29
Timestamp: 1705105113 Timestamp [UCT]: 2024-01-13 00:18:33 Age [y:d:h:m:s]: 01:313:05:27:46
Block: 934052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482684 RingCT/type: yes/0
Extra: 01649162e2dbef72cc15869826816af640ec0ec5fcce4649d3a27b11f7a6b73e290211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c28a8faaeaa5e4a0a8dcf5ea29d05c59ef631c18d8c9e4e9d3df7d44637180e 0.600000000000 1392038 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": 934062, "vin": [ { "gen": { "height": 934052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c28a8faaeaa5e4a0a8dcf5ea29d05c59ef631c18d8c9e4e9d3df7d44637180e" } } ], "extra": [ 1, 100, 145, 98, 226, 219, 239, 114, 204, 21, 134, 152, 38, 129, 106, 246, 64, 236, 14, 197, 252, 206, 70, 73, 211, 162, 123, 17, 247, 166, 183, 62, 41, 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