Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b44a228ad2fb9e5d95d446d09d50b9c1801bf7c8ca039e6bb957e7c381032f4

Tx prefix hash: 41527317caa70b60c0939fde0c307b22296118be5c1fb79dd1aa72719868e691
Tx public key: 2639d9400c080b9b0146131764298b06e6d6432d687bfd03b271df3b87f30c46
Timestamp: 1739365855 Timestamp [UTC]: 2025-02-12 13:10:55 Age [y:d:h:m:s]: 01:025:10:36:01
Block: 1217675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276720 RingCT/type: yes/0
Extra: 012639d9400c080b9b0146131764298b06e6d6432d687bfd03b271df3b87f30c46021100000003007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 556dceabb99b7df2dfcb42888c9b5c1b71a1ae52d238899b2265b26607c4f37b 0.000600000000 1704488 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": 1217685, "vin": [ { "gen": { "height": 1217675 } } ], "vout": [ { "amount": 600000000, "target": { "key": "556dceabb99b7df2dfcb42888c9b5c1b71a1ae52d238899b2265b26607c4f37b" } } ], "extra": [ 1, 38, 57, 217, 64, 12, 8, 11, 155, 1, 70, 19, 23, 100, 41, 139, 6, 230, 214, 67, 45, 104, 123, 253, 3, 178, 113, 223, 59, 135, 243, 12, 70, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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