Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97fcc6f3ec1fae8e3134fd6bd1c37f9d2cd7eb229571d04647d5bcc5a77362cd

Tx prefix hash: da98c0fa0af2ad7e0bce3c23cf6b0cc8624d198da31ed05d68ddf9eafef831ce
Tx public key: ef9f76b74b5f1be8d542278ef0db230120529d5738d7a09c7be5ad499fd88f4b
Timestamp: 1637511937 Timestamp [UCT]: 2021-11-21 16:25:37 Age [y:d:h:m:s]: 03:004:09:14:34
Block: 379080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 781994 RingCT/type: yes/0
Extra: 01ef9f76b74b5f1be8d542278ef0db230120529d5738d7a09c7be5ad499fd88f4b021100000012e9564d6f000000000000000000

1 output(s) for total of 34.036976788000 dcy

stealth address amount amount idx
00: e7b32a952194ed10410c8b89e704aa5e6b3ae5bbcf46e62dcb96f8d4dd4382e1 34.036976788000 766380 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": 379090, "vin": [ { "gen": { "height": 379080 } } ], "vout": [ { "amount": 34036976788, "target": { "key": "e7b32a952194ed10410c8b89e704aa5e6b3ae5bbcf46e62dcb96f8d4dd4382e1" } } ], "extra": [ 1, 239, 159, 118, 183, 75, 95, 27, 232, 213, 66, 39, 142, 240, 219, 35, 1, 32, 82, 157, 87, 56, 215, 160, 156, 123, 229, 173, 73, 159, 216, 143, 75, 2, 17, 0, 0, 0, 18, 233, 86, 77, 111, 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