Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebad8e9b129017861ff56b3ed8c0ba3e2f48215dee947c0cffa0cd148a346605

Tx prefix hash: 69f76a427a569d73d5ac86a06e7f859aeaf3329ec5c12460cf9f9e807989c4a4
Tx public key: 8b6e4f29f5bc6a9ceaea80b2e275e598769b4778b7e03bb78c1d25cac225939f
Timestamp: 1735964209 Timestamp [UTC]: 2025-01-04 04:16:49 Age [y:d:h:m:s]: 01:321:21:24:39
Block: 1189779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493715 RingCT/type: yes/0
Extra: 018b6e4f29f5bc6a9ceaea80b2e275e598769b4778b7e03bb78c1d25cac225939f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 59904f9be3e173e18f03631f337ff03aa2a6ad3477b2d44311ae3885aaa41c7e 0.000600000000 1676290 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": 1189789, "vin": [ { "gen": { "height": 1189779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59904f9be3e173e18f03631f337ff03aa2a6ad3477b2d44311ae3885aaa41c7e" } } ], "extra": [ 1, 139, 110, 79, 41, 245, 188, 106, 156, 234, 234, 128, 178, 226, 117, 229, 152, 118, 155, 71, 120, 183, 224, 59, 183, 140, 29, 37, 202, 194, 37, 147, 159, 2, 17, 0, 0, 0, 3, 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: