Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 352193b65fd89d92a9b08a3871048a976a89824ed2ee9ea291eca7d2b0cd5fe0

Tx prefix hash: 238d0dd752b2a29719e4a041ab3a008f1fae0447bb49d2cac576447dd23b5653
Tx public key: d35029042258218974284517bf61d75f095d03978d18a01f689e4ffee0d3fcbc
Timestamp: 1577426649 Timestamp [UCT]: 2019-12-27 06:04:09 Age [y:d:h:m:s]: 05:045:09:05:44
Block: 32696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1182176 RingCT/type: yes/0
Extra: 01d35029042258218974284517bf61d75f095d03978d18a01f689e4ffee0d3fcbc0211000000134ac5aa02000000000000000000

1 output(s) for total of 478.261517576000 dcy

stealth address amount amount idx
00: 3c080dee8a2647597cef9ab42b282474ce0d65aee4df6711c5ba9f76435e60e8 478.261517576000 54429 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": 32706, "vin": [ { "gen": { "height": 32696 } } ], "vout": [ { "amount": 478261517576, "target": { "key": "3c080dee8a2647597cef9ab42b282474ce0d65aee4df6711c5ba9f76435e60e8" } } ], "extra": [ 1, 211, 80, 41, 4, 34, 88, 33, 137, 116, 40, 69, 23, 191, 97, 215, 95, 9, 93, 3, 151, 141, 24, 160, 31, 104, 158, 79, 254, 224, 211, 252, 188, 2, 17, 0, 0, 0, 19, 74, 197, 170, 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