Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ce31fb5d59c0304f17f597021ab4d21f46584f9d7c5a09fe50386e759a62fcd

Tx prefix hash: 32249868a6f5202385f3ac27344993aff3c8c1872c63bd38ffbe740ec0ab77bf
Tx public key: 4be1a4ade99b8ddae39fc3f27451864d8db9b483c9f83404121c575fa232f8f6
Timestamp: 1770457292 Timestamp [UTC]: 2026-02-07 09:41:32 Age [y:d:h:m:s]: 00:009:16:42:25
Block: 1472570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 6891 RingCT/type: yes/0
Extra: 014be1a4ade99b8ddae39fc3f27451864d8db9b483c9f83404121c575fa232f8f602084317d9710aa79ae3

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6258e149848e147100bcff6b4f8cedf379166e6f7367eafa8b9d1f57f2d6cf6a 0.000600000000 1961850 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": 1472580, "vin": [ { "gen": { "height": 1472570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6258e149848e147100bcff6b4f8cedf379166e6f7367eafa8b9d1f57f2d6cf6a" } } ], "extra": [ 1, 75, 225, 164, 173, 233, 155, 141, 218, 227, 159, 195, 242, 116, 81, 134, 77, 141, 185, 180, 131, 201, 248, 52, 4, 18, 28, 87, 95, 162, 50, 248, 246, 2, 8, 67, 23, 217, 113, 10, 167, 154, 227 ], "rct_signatures": { "type": 0 } }


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