Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4951bf63b7efe6927f022db2f12e26b1f0690e546b4593068b32f5d0937437bc

Tx prefix hash: 70555ab3351ac35dfc57c1caad2e97943b92738b4460d7c7f5a1aa417ae23fb2
Tx public key: 0b8bb8722c48e1b60104ddeddd85daefd8000c8829c12b127a65df6db10b1739
Timestamp: 1772619888 Timestamp [UTC]: 2026-03-04 10:24:48 Age [y:d:h:m:s]: 00:261:07:04:34
Block: 1490433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192420 RingCT/type: yes/0
Extra: 010b8bb8722c48e1b60104ddeddd85daefd8000c8829c12b127a65df6db10b1739021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 49216e713cec84983b76ef7f056270f9aa2f77ba909c2e17fa5f5ceb4f93b947 0.000600000000 1979935 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": 1490443, "vin": [ { "gen": { "height": 1490433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49216e713cec84983b76ef7f056270f9aa2f77ba909c2e17fa5f5ceb4f93b947" } } ], "extra": [ 1, 11, 139, 184, 114, 44, 72, 225, 182, 1, 4, 221, 237, 221, 133, 218, 239, 216, 0, 12, 136, 41, 193, 43, 18, 122, 101, 223, 109, 177, 11, 23, 57, 2, 17, 0, 0, 0, 4, 228, 245, 25, 63, 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: