Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd1d8a4ae3760ffb6c2f38fc951783c36ef330cf419df1db52df70129e6468cf

Tx prefix hash: 7e24440a616d21a4c87441d4266e172b3fa24d062907dabb539b88d9ca3e1378
Tx public key: 77e079ba9e1108b0a35dcc61ef0bc2d46b9a3e0786b4c48f67b8974d12d80184
Timestamp: 1750212514 Timestamp [UTC]: 2025-06-18 02:08:34 Age [y:d:h:m:s]: 01:154:10:45:50
Block: 1307347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374548 RingCT/type: yes/0
Extra: 0177e079ba9e1108b0a35dcc61ef0bc2d46b9a3e0786b4c48f67b8974d12d80184021100000001e4dc9009000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ff20703c99f3b9868bf8962fe91639484d058caa721b8714fdff7add817be750 0.000600000000 1794958 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": 1307357, "vin": [ { "gen": { "height": 1307347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff20703c99f3b9868bf8962fe91639484d058caa721b8714fdff7add817be750" } } ], "extra": [ 1, 119, 224, 121, 186, 158, 17, 8, 176, 163, 93, 204, 97, 239, 11, 194, 212, 107, 154, 62, 7, 134, 180, 196, 143, 103, 184, 151, 77, 18, 216, 1, 132, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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: