Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78d895043e706d660c10db206e31827ca220360e96e7f3773f6d1310d2247ea0

Tx prefix hash: f04907ecb3195a9d8bda70d8eaff38f041b669697f8014ea3fff2ae1f46f9309
Tx public key: 735de7b53c17b2460b52f444c67b9df8e5d44b533c63e6347e1088e9bc21f332
Timestamp: 1768951614 Timestamp [UTC]: 2026-01-20 23:26:54 Age [y:d:h:m:s]: 00:114:20:44:20
Block: 1460105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74490 RingCT/type: yes/0
Extra: 01735de7b53c17b2460b52f444c67b9df8e5d44b533c63e6347e1088e9bc21f33202110000000949d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aa57139558c694bbed71a3265c782e8f21d3bbd775cc808c6171f703d8fc92f0 0.000600000000 1949273 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": 1460115, "vin": [ { "gen": { "height": 1460105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa57139558c694bbed71a3265c782e8f21d3bbd775cc808c6171f703d8fc92f0" } } ], "extra": [ 1, 115, 93, 231, 181, 60, 23, 178, 70, 11, 82, 244, 68, 198, 123, 157, 248, 229, 212, 75, 83, 60, 99, 230, 52, 126, 16, 136, 233, 188, 33, 243, 50, 2, 17, 0, 0, 0, 9, 73, 215, 62, 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: