Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c80178e0dc714a00932fc3e308ef35e37b8cc279fbda37de6f808903f145f9cf

Tx prefix hash: 148164e3e4788fc6de38e1e602ebdd5880113d8a04e0be3d0dfa3378e446539f
Tx public key: 3875e5d12ca5bb15bdcdcf560dc7631b1a5b0158f0e3c31bca51e1b2b61ce877
Timestamp: 1583849262 Timestamp [UCT]: 2020-03-10 14:07:42 Age [y:d:h:m:s]: 05:040:20:49:01
Block: 79672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1185126 RingCT/type: yes/0
Extra: 013875e5d12ca5bb15bdcdcf560dc7631b1a5b0158f0e3c31bca51e1b2b61ce877021100000001995a6b02000000000000000000

1 output(s) for total of 334.206106574000 dcy

stealth address amount amount idx
00: 534deaeae2b8156d0f97dcac6c35a2c28e917fdaaa51b7d971bf7e4a500ffbda 334.206106574000 145820 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": 79682, "vin": [ { "gen": { "height": 79672 } } ], "vout": [ { "amount": 334206106574, "target": { "key": "534deaeae2b8156d0f97dcac6c35a2c28e917fdaaa51b7d971bf7e4a500ffbda" } } ], "extra": [ 1, 56, 117, 229, 209, 44, 165, 187, 21, 189, 205, 207, 86, 13, 199, 99, 27, 26, 91, 1, 88, 240, 227, 195, 27, 202, 81, 225, 178, 182, 28, 232, 119, 2, 17, 0, 0, 0, 1, 153, 90, 107, 2, 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