Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6ef110abac9531ee6249e83f0fbb9d9a7950d2e905c604c43bc7e5c1cb8191d

Tx prefix hash: ac235f454fd356c26ad1c81463fc2f6821d6635156d4e1589b47445c7f9552a3
Tx public key: a0b9567da6ce9febeed41815319f8737738828a7605035f995b21b90ae077d06
Timestamp: 1580887794 Timestamp [UCT]: 2020-02-05 07:29:54 Age [y:d:h:m:s]: 05:273:22:04:45
Block: 58976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1345601 RingCT/type: yes/0
Extra: 01a0b9567da6ce9febeed41815319f8737738828a7605035f995b21b90ae077d0602110000000249b77a3d000000000000000000

1 output(s) for total of 391.371187244000 dcy

stealth address amount amount idx
00: 6aafe780043b4585d5f3a7902f8670100386c8ff30e02d6f951f92b3cb55bc1b 391.371187244000 108942 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": 58986, "vin": [ { "gen": { "height": 58976 } } ], "vout": [ { "amount": 391371187244, "target": { "key": "6aafe780043b4585d5f3a7902f8670100386c8ff30e02d6f951f92b3cb55bc1b" } } ], "extra": [ 1, 160, 185, 86, 125, 166, 206, 159, 235, 238, 212, 24, 21, 49, 159, 135, 55, 115, 136, 40, 167, 96, 80, 53, 249, 149, 178, 27, 144, 174, 7, 125, 6, 2, 17, 0, 0, 0, 2, 73, 183, 122, 61, 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