Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b8747b8e9ca36b34e599391181ada0cfeb5aae9badf0d555c7372bc7cb8b62c

Tx prefix hash: b2b8750808473bd280a8e7f2e0cf2a0dbc76f7bbb5f2fd2d934b8d0d9a40fb16
Tx public key: fbc42fac939d04f7a04320cae89c66c4b2c28f4742f82e1ee89550a95aafc082
Timestamp: 1738110737 Timestamp [UTC]: 2025-01-29 00:32:17 Age [y:d:h:m:s]: 01:108:11:03:54
Block: 1207290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328558 RingCT/type: yes/0
Extra: 01fbc42fac939d04f7a04320cae89c66c4b2c28f4742f82e1ee89550a95aafc0820211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a5614c64210246a5debc0661fdd1173efd2d8aaf21307814670c69cbdeb6c1c1 0.000600000000 1694013 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": 1207300, "vin": [ { "gen": { "height": 1207290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5614c64210246a5debc0661fdd1173efd2d8aaf21307814670c69cbdeb6c1c1" } } ], "extra": [ 1, 251, 196, 47, 172, 147, 157, 4, 247, 160, 67, 32, 202, 232, 156, 102, 196, 178, 194, 143, 71, 66, 248, 46, 30, 232, 149, 80, 169, 90, 175, 192, 130, 2, 17, 0, 0, 0, 2, 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: