Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71197318e4449ed05e52615b87e2e4d811737a87ddaa3c833246b55e6537a2d3

Tx prefix hash: 28932db877e6463f0812f87d6a9a0c2988a73c6a3e7bf5038b7430f2094dda2e
Tx public key: 37403f6b4ae56f70a4b8669f766672f34944daf3277e9ea94958ec87669e940a
Timestamp: 1582517738 Timestamp [UCT]: 2020-02-24 04:15:38 Age [y:d:h:m:s]: 04:256:00:48:16
Block: 71439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1075422 RingCT/type: yes/0
Extra: 0137403f6b4ae56f70a4b8669f766672f34944daf3277e9ea94958ec87669e940a02110000000156c366d3000000000000000000

1 output(s) for total of 355.871934251000 dcy

stealth address amount amount idx
00: e532257351311c9ed97cd8b825edfef04a28ecc4889dfe29f079a7f65b3f4322 355.871934251000 131938 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": 71449, "vin": [ { "gen": { "height": 71439 } } ], "vout": [ { "amount": 355871934251, "target": { "key": "e532257351311c9ed97cd8b825edfef04a28ecc4889dfe29f079a7f65b3f4322" } } ], "extra": [ 1, 55, 64, 63, 107, 74, 229, 111, 112, 164, 184, 102, 159, 118, 102, 114, 243, 73, 68, 218, 243, 39, 126, 158, 169, 73, 88, 236, 135, 102, 158, 148, 10, 2, 17, 0, 0, 0, 1, 86, 195, 102, 211, 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