Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba63d91d6780737ae3d503345dba2bfdb9b3808ad789d51206dc9976ef200898

Tx prefix hash: bf2cfe6eca267ea89c738e79411af612f2b649dfadb528e9e3c1f893649e133a
Tx public key: 6792ab5ec161419baea4c6c812598d75c100150ec10a1004ea71b7ed0dd1da4b
Timestamp: 1744312488 Timestamp [UTC]: 2025-04-10 19:14:48 Age [y:d:h:m:s]: 01:032:03:54:34
Block: 1258615 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273806 RingCT/type: yes/0
Extra: 016792ab5ec161419baea4c6c812598d75c100150ec10a1004ea71b7ed0dd1da4b0211000000066c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fed8b3c7934ffcd08a181d6ded3f1260f4b785f1cea88944d1306347d603d53a 0.000600000000 1745752 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": 1258625, "vin": [ { "gen": { "height": 1258615 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fed8b3c7934ffcd08a181d6ded3f1260f4b785f1cea88944d1306347d603d53a" } } ], "extra": [ 1, 103, 146, 171, 94, 193, 97, 65, 155, 174, 164, 198, 200, 18, 89, 141, 117, 193, 0, 21, 14, 193, 10, 16, 4, 234, 113, 183, 237, 13, 209, 218, 75, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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: