Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e482f73df3da2bb55905a83aabac38956a9fb4fb9330f18c3e9f3556487fe946

Tx prefix hash: c696e2e0a97516fbc5eb008296ed1c0db37fd367fb7a55d67820ab8286791d79
Tx public key: 5516abbd3ca4ff5042392f1a6649820da5a4ef18ef391dfb11dbdab4d965fb57
Timestamp: 1577732877 Timestamp [UCT]: 2019-12-30 19:07:57 Age [y:d:h:m:s]: 04:331:21:41:29
Block: 35259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126267 RingCT/type: yes/0
Extra: 015516abbd3ca4ff5042392f1a6649820da5a4ef18ef391dfb11dbdab4d965fb57021100000007feadaf7f000000000000000000

1 output(s) for total of 469.043012783000 dcy

stealth address amount amount idx
00: a3c809de83f6afeaeb0fcdbc5d4c43ead928457b0d1f1ed12c29778f1a62d074 469.043012783000 59373 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": 35269, "vin": [ { "gen": { "height": 35259 } } ], "vout": [ { "amount": 469043012783, "target": { "key": "a3c809de83f6afeaeb0fcdbc5d4c43ead928457b0d1f1ed12c29778f1a62d074" } } ], "extra": [ 1, 85, 22, 171, 189, 60, 164, 255, 80, 66, 57, 47, 26, 102, 73, 130, 13, 165, 164, 239, 24, 239, 57, 29, 251, 17, 219, 218, 180, 217, 101, 251, 87, 2, 17, 0, 0, 0, 7, 254, 173, 175, 127, 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