Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37aff9f71ff50566ecdc1a652d061588e03d8f5e57a1bfb380db7d3229f0938b

Tx prefix hash: 091000e227d4605161d300cfa9ed1ac6637644c11236e12ac226f1bd35138fa8
Tx public key: 389acfd4a70aefe203071f943addd9460c1c0c5e084ee74b340ba07c55e0576a
Timestamp: 1742399676 Timestamp [UTC]: 2025-03-19 15:54:36 Age [y:d:h:m:s]: 01:057:12:49:12
Block: 1242798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292074 RingCT/type: yes/0
Extra: 01389acfd4a70aefe203071f943addd9460c1c0c5e084ee74b340ba07c55e0576a02110000000abfa77623000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4679a186ced52f5c2ec12f6c7437ec36a18c4727fd1f6765a0a8554403ef1f2e 0.000600000000 1729777 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": 1242808, "vin": [ { "gen": { "height": 1242798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4679a186ced52f5c2ec12f6c7437ec36a18c4727fd1f6765a0a8554403ef1f2e" } } ], "extra": [ 1, 56, 154, 207, 212, 167, 10, 239, 226, 3, 7, 31, 148, 58, 221, 217, 70, 12, 28, 12, 94, 8, 78, 231, 75, 52, 11, 160, 124, 85, 224, 87, 106, 2, 17, 0, 0, 0, 10, 191, 167, 118, 35, 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) | monero version: