Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e2b1da5d976381c88135e260356d937192c5131932764aa62f5bd144b4a642d

Tx prefix hash: ff7f8898a3fc545f31b411805d2fd08a456e123d5d1d23374ae436bff98d22a6
Tx public key: 8d2af5c864e0eea815829c2fc298728a0aa566df842c34df8c48ee9dfdeb3298
Timestamp: 1580263761 Timestamp [UCT]: 2020-01-29 02:09:21 Age [y:d:h:m:s]: 04:330:03:31:01
Block: 54317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126945 RingCT/type: yes/0
Extra: 018d2af5c864e0eea815829c2fc298728a0aa566df842c34df8c48ee9dfdeb3298021100000001391a8d0e000000000000000000

1 output(s) for total of 405.532866624000 dcy

stealth address amount amount idx
00: 4e986ebcffd4787d0b332a3cc3e058249f5a72aadfd88ec27879fac1eb131768 405.532866624000 100667 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": 54327, "vin": [ { "gen": { "height": 54317 } } ], "vout": [ { "amount": 405532866624, "target": { "key": "4e986ebcffd4787d0b332a3cc3e058249f5a72aadfd88ec27879fac1eb131768" } } ], "extra": [ 1, 141, 42, 245, 200, 100, 224, 238, 168, 21, 130, 156, 47, 194, 152, 114, 138, 10, 165, 102, 223, 132, 44, 52, 223, 140, 72, 238, 157, 253, 235, 50, 152, 2, 17, 0, 0, 0, 1, 57, 26, 141, 14, 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