Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53d530d9562df98df95ef46228ad7db880262ea3f8d04e2675370a558f7e4e9c

Tx prefix hash: 1aa3702f2e765eab7dbbc61d6bf9ab53390cd51955a3e8f99bfccf431229c891
Tx public key: 43be838ca10dac5bc4f573a0fc58473e3f97bdbd0a7e77ae724536a2748ab18c
Timestamp: 1742597913 Timestamp [UTC]: 2025-03-21 22:58:33 Age [y:d:h:m:s]: 01:244:17:14:43
Block: 1244424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439070 RingCT/type: yes/0
Extra: 0143be838ca10dac5bc4f573a0fc58473e3f97bdbd0a7e77ae724536a2748ab18c021100000003af845649000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 672804275e3f00f359c4408c0deff5064366d56df86bcb5875fae296234f6140 0.000600000000 1731415 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": 1244434, "vin": [ { "gen": { "height": 1244424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "672804275e3f00f359c4408c0deff5064366d56df86bcb5875fae296234f6140" } } ], "extra": [ 1, 67, 190, 131, 140, 161, 13, 172, 91, 196, 245, 115, 160, 252, 88, 71, 62, 63, 151, 189, 189, 10, 126, 119, 174, 114, 69, 54, 162, 116, 138, 177, 140, 2, 17, 0, 0, 0, 3, 175, 132, 86, 73, 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: