Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fab97fabaeba9d814f62f97b2e51f1594a9cf6d9ff3d95d6ec98185db53ca1bd

Tx prefix hash: 4df23b3ce530789a8e724ddb31ce8fdeeda98668fa897ffeb0aea161bad7c550
Tx public key: 1bf588350f4dbfa1f66e7468972ae4dd49e9d4e920809180e57ca5a20746617b
Timestamp: 1749016793 Timestamp [UTC]: 2025-06-04 05:59:53 Age [y:d:h:m:s]: 01:163:08:56:29
Block: 1297580 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380629 RingCT/type: yes/0
Extra: 011bf588350f4dbfa1f66e7468972ae4dd49e9d4e920809180e57ca5a20746617b02110000000f43846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c12f604e73358fa08ae6a8bd66fe5d89c06a4cfb48442584ad1036dc58d6ba32 0.000600000000 1785101 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": 1297590, "vin": [ { "gen": { "height": 1297580 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c12f604e73358fa08ae6a8bd66fe5d89c06a4cfb48442584ad1036dc58d6ba32" } } ], "extra": [ 1, 27, 245, 136, 53, 15, 77, 191, 161, 246, 110, 116, 104, 151, 42, 228, 221, 73, 233, 212, 233, 32, 128, 145, 128, 229, 124, 165, 162, 7, 70, 97, 123, 2, 17, 0, 0, 0, 15, 67, 132, 109, 102, 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: