Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f96fd6a575ae3f870da073b25f3eac234bc2e8a239124d013a157cf0122ae3fa

Tx prefix hash: 843a724ac52eea0e81c0bc0e32db9e0728a5d29ac6399c0b6135a0a6f21a99c9
Tx public key: 3ee8c5a530b5b336229bea3f3a58526bbfb297bd77218c11ae851db76094c62b
Timestamp: 1742212816 Timestamp [UTC]: 2025-03-17 12:00:16 Age [y:d:h:m:s]: 01:072:00:51:07
Block: 1241256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304102 RingCT/type: yes/0
Extra: 013ee8c5a530b5b336229bea3f3a58526bbfb297bd77218c11ae851db76094c62b0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 481fe8a9d1590a5a487eba4418b0ca0039ab869e97f3d04d0c80f5dba10f807d 0.000600000000 1728229 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": 1241266, "vin": [ { "gen": { "height": 1241256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "481fe8a9d1590a5a487eba4418b0ca0039ab869e97f3d04d0c80f5dba10f807d" } } ], "extra": [ 1, 62, 232, 197, 165, 48, 181, 179, 54, 34, 155, 234, 63, 58, 88, 82, 107, 191, 178, 151, 189, 119, 33, 140, 17, 174, 133, 29, 183, 96, 148, 198, 43, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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: