Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b81ad6533a4697d05577f6fb15f2ed95a3d586c2afc0b54a8b7037b2659b4b29

Tx prefix hash: 21b510eef4a1ef8786053904dde682b311ed16b796559952cb52e770e471c6e5
Tx public key: 32a50963dbc439567540528a6ef6f37904aaeb71c5aa7fea3ba35552f22e228a
Timestamp: 1580974844 Timestamp [UCT]: 2020-02-06 07:40:44 Age [y:d:h:m:s]: 04:256:00:57:12
Block: 59542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1074630 RingCT/type: yes/0
Extra: 0132a50963dbc439567540528a6ef6f37904aaeb71c5aa7fea3ba35552f22e228a0211000000037adf42d3000000000000000000

1 output(s) for total of 389.684790901000 dcy

stealth address amount amount idx
00: 8df950514a8db8684d71f433e6f22aa6391e46fdfb688edce0d1966e943065dc 389.684790901000 109958 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": 59552, "vin": [ { "gen": { "height": 59542 } } ], "vout": [ { "amount": 389684790901, "target": { "key": "8df950514a8db8684d71f433e6f22aa6391e46fdfb688edce0d1966e943065dc" } } ], "extra": [ 1, 50, 165, 9, 99, 219, 196, 57, 86, 117, 64, 82, 138, 110, 246, 243, 121, 4, 170, 235, 113, 197, 170, 127, 234, 59, 163, 85, 82, 242, 46, 34, 138, 2, 17, 0, 0, 0, 3, 122, 223, 66, 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