Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2effa38e598646bf415e0862ce143f53c3438deaa7060b591c2ba666615c7b7

Tx prefix hash: b1c6f60f2e5cfcdb9b312cb793b9096bf14da84d2cffe5b985c91092fd66fd5f
Tx public key: 908a8c7ad06f8b8b4a4da4d322317234cd21c3c1f53bda961384de5299493611
Timestamp: 1770966289 Timestamp [UTC]: 2026-02-13 07:04:49 Age [y:d:h:m:s]: 00:001:02:04:26
Block: 1476769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 747 RingCT/type: yes/0
Extra: 01908a8c7ad06f8b8b4a4da4d322317234cd21c3c1f53bda961384de52994936110208b1c5733f01db8fa4

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cf1fd1c86fdad97692114bde882e2a5b7a9984f0ab053bfcaf8d7cdbe068ca5a 0.000600000000 1966079 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": 1476779, "vin": [ { "gen": { "height": 1476769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf1fd1c86fdad97692114bde882e2a5b7a9984f0ab053bfcaf8d7cdbe068ca5a" } } ], "extra": [ 1, 144, 138, 140, 122, 208, 111, 139, 139, 74, 77, 164, 211, 34, 49, 114, 52, 205, 33, 195, 193, 245, 59, 218, 150, 19, 132, 222, 82, 153, 73, 54, 17, 2, 8, 177, 197, 115, 63, 1, 219, 143, 164 ], "rct_signatures": { "type": 0 } }


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