Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a78bcb04de656abd654e041d865a913d0de6bdeb249115cd5946977cf2b4957

Tx prefix hash: 218aad9bde8c091a336b12037a4d3abf86be2460568f400c7c84a6560fa775a0
Tx public key: 6df39c5323ed68ecc9abd169e422add413b44d10405a1f78356832170d6db84a
Timestamp: 1718757884 Timestamp [UTC]: 2024-06-19 00:44:44 Age [y:d:h:m:s]: 02:154:02:54:36
Block: 1047264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 635108 RingCT/type: yes/0
Extra: 016df39c5323ed68ecc9abd169e422add413b44d10405a1f78356832170d6db84a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 17a4c64db99b8c45fec4a23c376f0aa7543c8d9875cea804809e05740240d0b8 0.000600000000 1517083 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": 1047274, "vin": [ { "gen": { "height": 1047264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17a4c64db99b8c45fec4a23c376f0aa7543c8d9875cea804809e05740240d0b8" } } ], "extra": [ 1, 109, 243, 156, 83, 35, 237, 104, 236, 201, 171, 209, 105, 228, 34, 173, 212, 19, 180, 77, 16, 64, 90, 31, 120, 53, 104, 50, 23, 13, 109, 184, 74, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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: