Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 590cd21901438560c507fe687ab39c31d5eb628fa69e5713300124d8dd88362c

Tx prefix hash: 5aeaefe678caf022923628564306dcca140832f4abf45b830993671d77f57b51
Tx public key: e7f59859f0ee9cab7a1fa0d9ce13cc2ddfd74abd6abd3483a835098d2ed8e6b1
Timestamp: 1576928175 Timestamp [UCT]: 2019-12-21 11:36:15 Age [y:d:h:m:s]: 05:143:14:22:25
Block: 29256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1251738 RingCT/type: yes/0
Extra: 01e7f59859f0ee9cab7a1fa0d9ce13cc2ddfd74abd6abd3483a835098d2ed8e6b1021100000029ad433a0b000000000000000000

1 output(s) for total of 490.979761541000 dcy

stealth address amount amount idx
00: 7ae181f7e2af6b34d16add691fec6dc0ad0243987a138d08869855064f047506 490.979761541000 48084 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": 29266, "vin": [ { "gen": { "height": 29256 } } ], "vout": [ { "amount": 490979761541, "target": { "key": "7ae181f7e2af6b34d16add691fec6dc0ad0243987a138d08869855064f047506" } } ], "extra": [ 1, 231, 245, 152, 89, 240, 238, 156, 171, 122, 31, 160, 217, 206, 19, 204, 45, 223, 215, 74, 189, 106, 189, 52, 131, 168, 53, 9, 141, 46, 216, 230, 177, 2, 17, 0, 0, 0, 41, 173, 67, 58, 11, 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