Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8801567f957796379f18d335ea304d29975def529a5ad79d92311d6e5cb0676d

Tx prefix hash: d5df4ed86adc84fef052f86d2c9c2a971adafddb9b3a0cc9cb16954e702f9de6
Tx public key: 5b80bff579ce0d566d82d39689f84270ebcdf080f474e34d0abe337d805a49c5
Timestamp: 1645406413 Timestamp [UCT]: 2022-02-21 01:20:13 Age [y:d:h:m:s]: 02:357:01:35:08
Block: 443008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 774356 RingCT/type: yes/0
Extra: 015b80bff579ce0d566d82d39689f84270ebcdf080f474e34d0abe337d805a49c50211000000024a0f5013000000000000000000

1 output(s) for total of 20.899258784000 dcy

stealth address amount amount idx
00: 2dd76b676cee2f5494a0df04b352fdcc78de408b02deaf8361fee4a6778667d5 20.899258784000 855929 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": 443018, "vin": [ { "gen": { "height": 443008 } } ], "vout": [ { "amount": 20899258784, "target": { "key": "2dd76b676cee2f5494a0df04b352fdcc78de408b02deaf8361fee4a6778667d5" } } ], "extra": [ 1, 91, 128, 191, 245, 121, 206, 13, 86, 109, 130, 211, 150, 137, 248, 66, 112, 235, 205, 240, 128, 244, 116, 227, 77, 10, 190, 51, 125, 128, 90, 73, 197, 2, 17, 0, 0, 0, 2, 74, 15, 80, 19, 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