Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89b2dba87f5200eded27c15784b9cb52ce291988f72c3175dcb2c78544bb3f1a

Tx prefix hash: 88ceb267d6ca3b09a29710173aed312cfadf61508efa8dfbe81e77008340d95a
Tx public key: 5aaf00ceb3fa201a0122daf8da0100367604adbf9f88e62f1216ace3b23d1c2e
Timestamp: 1722066016 Timestamp [UTC]: 2024-07-27 07:40:16 Age [y:d:h:m:s]: 01:224:02:56:52
Block: 1074680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418627 RingCT/type: yes/0
Extra: 015aaf00ceb3fa201a0122daf8da0100367604adbf9f88e62f1216ace3b23d1c2e02110000000591e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 097d9209749198edccf0a88bcc24a1cb5ee0ecce2403cb2d367d5ccf5a6f5dc9 0.000600000000 1547197 of 15 -

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": 1074690, "vin": [ { "gen": { "height": 1074680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "097d9209749198edccf0a88bcc24a1cb5ee0ecce2403cb2d367d5ccf5a6f5dc9" } } ], "extra": [ 1, 90, 175, 0, 206, 179, 250, 32, 26, 1, 34, 218, 248, 218, 1, 0, 54, 118, 4, 173, 191, 159, 136, 230, 47, 18, 22, 172, 227, 178, 61, 28, 46, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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