Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb444aa1af8e582a6c2f7f99ca8dc3c546e3409fa76a913343f56e0e63ce651b

Tx prefix hash: 061a73e8ca94d058d7d261849763d1910183b7257fa89622e494d55b7fa46541
Tx public key: fc2b0664f0e2cffbed0b7c6a17429d3deb653a2de84c9a6457936227e570d22e
Timestamp: 1751608342 Timestamp [UTC]: 2025-07-04 05:52:22 Age [y:d:h:m:s]: 01:139:10:48:36
Block: 1318425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364405 RingCT/type: yes/0
Extra: 01fc2b0664f0e2cffbed0b7c6a17429d3deb653a2de84c9a6457936227e570d22e02110000000100f080dd000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fe228d7d64a444df4698251ea58e81f29636fe41f069e0a54d6e1c5a30a4c2ff 0.000600000000 1806106 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": 1318435, "vin": [ { "gen": { "height": 1318425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe228d7d64a444df4698251ea58e81f29636fe41f069e0a54d6e1c5a30a4c2ff" } } ], "extra": [ 1, 252, 43, 6, 100, 240, 226, 207, 251, 237, 11, 124, 106, 23, 66, 157, 61, 235, 101, 58, 45, 232, 76, 154, 100, 87, 147, 98, 39, 229, 112, 210, 46, 2, 17, 0, 0, 0, 1, 0, 240, 128, 221, 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: