Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bed8f545950e60061c76c2e2df0aaffbf7a25c20b1f70fc5c91ad2568f0766d

Tx prefix hash: 3770161aa07244e2b1d4bd834078411420dd3dfb07844cc84268b2d16dda960f
Tx public key: 48e98ffb681404ccc3a39506ca0abf54f9f02330d1714b372ee898f35d8cb681
Timestamp: 1744370802 Timestamp [UTC]: 2025-04-11 11:26:42 Age [y:d:h:m:s]: 01:033:15:26:24
Block: 1259108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274942 RingCT/type: yes/0
Extra: 0148e98ffb681404ccc3a39506ca0abf54f9f02330d1714b372ee898f35d8cb681021100000005a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c8f7d9eeba2b7ddd91c87a66af39946b307b365ba4b2340444df5b3016c306a4 0.000600000000 1746247 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": 1259118, "vin": [ { "gen": { "height": 1259108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8f7d9eeba2b7ddd91c87a66af39946b307b365ba4b2340444df5b3016c306a4" } } ], "extra": [ 1, 72, 233, 143, 251, 104, 20, 4, 204, 195, 163, 149, 6, 202, 10, 191, 84, 249, 240, 35, 48, 209, 113, 75, 55, 46, 232, 152, 243, 93, 140, 182, 129, 2, 17, 0, 0, 0, 5, 161, 29, 186, 152, 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: