Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73a5f60dcac3b82d9a4ab58067e4c12c2b87a732185e19cff6818612873365ce

Tx prefix hash: 81342afeee0f3b680f4a4215a13920ef1756f75d5e9614bdaacde7af567feaa1
Tx public key: d4404b6c007f3005f169ea08d1d2f2da649a4ce5fbbb1058947b7441599b7601
Timestamp: 1577219014 Timestamp [UCT]: 2019-12-24 20:23:34 Age [y:d:h:m:s]: 05:016:16:57:41
Block: 31010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161897 RingCT/type: yes/0
Extra: 01d4404b6c007f3005f169ea08d1d2f2da649a4ce5fbbb1058947b7441599b76010211000000adac34bf9e000000000000000000

1 output(s) for total of 484.453232358000 dcy

stealth address amount amount idx
00: b6291ee2fd26abcf2d42640d571d5deea8e161dc0fb163ec721fb85044853bb8 484.453232358000 51214 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": 31020, "vin": [ { "gen": { "height": 31010 } } ], "vout": [ { "amount": 484453232358, "target": { "key": "b6291ee2fd26abcf2d42640d571d5deea8e161dc0fb163ec721fb85044853bb8" } } ], "extra": [ 1, 212, 64, 75, 108, 0, 127, 48, 5, 241, 105, 234, 8, 209, 210, 242, 218, 100, 154, 76, 229, 251, 187, 16, 88, 148, 123, 116, 65, 89, 155, 118, 1, 2, 17, 0, 0, 0, 173, 172, 52, 191, 158, 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