Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f342f1cb62265d1d77f5beb71ac5a07be5eb211712b9e8fb42e6a29a657acf8e

Tx prefix hash: 53f8ce28f5401c2f4c5cc9eb2bb7713905b57b35de7b6ea50f86e5628466250f
Tx public key: 91a7065c01576002aa98a3463fcba72805ea26b0166e1b6dca46ae3867ffcd6a
Timestamp: 1578430985 Timestamp [UTC]: 2020-01-07 21:03:05 Age [y:d:h:m:s]: 06:042:14:53:42
Block: 40769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1438975 RingCT/type: yes/0
Extra: 0191a7065c01576002aa98a3463fcba72805ea26b0166e1b6dca46ae3867ffcd6a0211000000078a2ee0d9000000000000000000

1 output(s) for total of 0.449700871654 xmr

stealth address amount amount idx tag
00: 407738ecc0f8db5ebafaa427d9147d7d4c5f4e5f0013a884779522cd5b019647 0.449700871654 71911 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 dinastycoin-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": 40779, "vin": [ { "gen": { "height": 40769 } } ], "vout": [ { "amount": 449700871654, "target": { "key": "407738ecc0f8db5ebafaa427d9147d7d4c5f4e5f0013a884779522cd5b019647" } } ], "extra": [ 1, 145, 167, 6, 92, 1, 87, 96, 2, 170, 152, 163, 70, 63, 203, 167, 40, 5, 234, 38, 176, 22, 110, 27, 109, 202, 70, 174, 56, 103, 255, 205, 106, 2, 17, 0, 0, 0, 7, 138, 46, 224, 217, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369