Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0d610f8bddf2e51292629518ddf46f1c78dcaecad2b31559eadb942186cd80d

Tx prefix hash: 3f6a9537f798c85d87898528a73261a9c2e70b95f1f411460a48ab23c1030524
Tx public key: d9f051788940bae0f02d67abcd56884b17808b82e0d184143630fbe510e67e76
Timestamp: 1705162178 Timestamp [UTC]: 2024-01-13 16:09:38 Age [y:d:h:m:s]: 02:119:11:32:36
Block: 934529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597285 RingCT/type: yes/0
Extra: 01d9f051788940bae0f02d67abcd56884b17808b82e0d184143630fbe510e67e76021100000001ac328d11000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: dccdd44dc7dafb1a18198047a446fb1bf137f0b5c9702bc9fbdad76ef6d78b16 0.000600000000 1392543 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": 934539, "vin": [ { "gen": { "height": 934529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dccdd44dc7dafb1a18198047a446fb1bf137f0b5c9702bc9fbdad76ef6d78b16" } } ], "extra": [ 1, 217, 240, 81, 120, 137, 64, 186, 224, 240, 45, 103, 171, 205, 86, 136, 75, 23, 128, 139, 130, 224, 209, 132, 20, 54, 48, 251, 229, 16, 230, 126, 118, 2, 17, 0, 0, 0, 1, 172, 50, 141, 17, 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: