Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3fcd7f7afe4f237782b7e1edc68e6d4674643d833e9163fe0728e2e4da46eb7

Tx prefix hash: dc7d436f22de2796ae686b2adb76066920774a3d7d2860624512f77589125a23
Tx public key: c19b33ba569f08b66a46749e5717a57ad1581080fd40dd2fe8e0be0c4094cd52
Timestamp: 1745832884 Timestamp [UTC]: 2025-04-28 09:34:44 Age [y:d:h:m:s]: 01:201:09:44:44
Block: 1271210 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407897 RingCT/type: yes/0
Extra: 01c19b33ba569f08b66a46749e5717a57ad1581080fd40dd2fe8e0be0c4094cd5202110000000325a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 344f2b932c10ea9005407df8ecded5910e3d62a439b224127a9ebcc07afc163d 0.000600000000 1758465 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": 1271220, "vin": [ { "gen": { "height": 1271210 } } ], "vout": [ { "amount": 600000000, "target": { "key": "344f2b932c10ea9005407df8ecded5910e3d62a439b224127a9ebcc07afc163d" } } ], "extra": [ 1, 193, 155, 51, 186, 86, 159, 8, 182, 106, 70, 116, 158, 87, 23, 165, 122, 209, 88, 16, 128, 253, 64, 221, 47, 232, 224, 190, 12, 64, 148, 205, 82, 2, 17, 0, 0, 0, 3, 37, 163, 90, 15, 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: