Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c62c65f02bcfa24855905cb70e544f52ce27a770bfa5db5e947e9f4911d03521

Tx prefix hash: 82d93318f7259a7244828c00c5266b3930b97e43963a0b59de5c0cf1ae3e3ccd
Tx public key: 1db34c41fb29d3f17e3dbbdcf00f3cb4dca5f23ed4c559a62d507b1cd654e391
Timestamp: 1682891545 Timestamp [UCT]: 2023-04-30 21:52:25 Age [y:d:h:m:s]: 01:302:19:26:30
Block: 750164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477637 RingCT/type: yes/0
Extra: 011db34c41fb29d3f17e3dbbdcf00f3cb4dca5f23ed4c559a62d507b1cd654e3910211000000027e406890000000000000000000

1 output(s) for total of 2.006298105000 dcy

stealth address amount amount idx
00: 78d00604daa10ce36956e84bdefcdd1481df15416271fbf6d5184507c4631ed2 2.006298105000 1198213 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": 750174, "vin": [ { "gen": { "height": 750164 } } ], "vout": [ { "amount": 2006298105, "target": { "key": "78d00604daa10ce36956e84bdefcdd1481df15416271fbf6d5184507c4631ed2" } } ], "extra": [ 1, 29, 179, 76, 65, 251, 41, 211, 241, 126, 61, 187, 220, 240, 15, 60, 180, 220, 165, 242, 62, 212, 197, 89, 166, 45, 80, 123, 28, 214, 84, 227, 145, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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