Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32c6c4f27d4f7e5f69f7ee4d9b40de3201ab97109df81bcd1a1d5747c0cb6872

Tx prefix hash: 38bf943e27c123d8526d2fc6671b5f2b60a60ddd078522cbecca46bcc682813a
Tx public key: db210f4c0c4b7c743a38f4021e919777d0371d970e3ea46b32f61524df527978
Timestamp: 1744264910 Timestamp [UTC]: 2025-04-10 06:01:50 Age [y:d:h:m:s]: 01:033:06:20:56
Block: 1258223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274613 RingCT/type: yes/0
Extra: 01db210f4c0c4b7c743a38f4021e919777d0371d970e3ea46b32f61524df52797802110000000c6c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4bed44d0afaa66682e060a8b65fee17b905c2a4167d99fee4a1981168f8cbce7 0.000600000000 1745356 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": 1258233, "vin": [ { "gen": { "height": 1258223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bed44d0afaa66682e060a8b65fee17b905c2a4167d99fee4a1981168f8cbce7" } } ], "extra": [ 1, 219, 33, 15, 76, 12, 75, 124, 116, 58, 56, 244, 2, 30, 145, 151, 119, 208, 55, 29, 151, 14, 62, 164, 107, 50, 246, 21, 36, 223, 82, 121, 120, 2, 17, 0, 0, 0, 12, 108, 152, 170, 61, 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: