Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d52f04005e35e9cf7a0d11dde28f7ef2bdce7f6f75204f0ce6c58d88f8fde746

Tx prefix hash: 1903748104b322e0bb746e37e1e20afdb35b972b9862467d745d06670a42f877
Tx public key: d92fe1b660631e68ecea73d4fcc75f605d3e1396fa5bcde31c3bd5a6ca765da2
Timestamp: 1714505917 Timestamp [UTC]: 2024-04-30 19:38:37 Age [y:d:h:m:s]: 02:200:18:53:27
Block: 1012003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 668438 RingCT/type: yes/0
Extra: 01d92fe1b660631e68ecea73d4fcc75f605d3e1396fa5bcde31c3bd5a6ca765da20211000000040011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5c7d745922f0a17cb968aee0ea0a1f360a4724c1f28c195c92055fc20667eda8 0.000600000000 1474401 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": 1012013, "vin": [ { "gen": { "height": 1012003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c7d745922f0a17cb968aee0ea0a1f360a4724c1f28c195c92055fc20667eda8" } } ], "extra": [ 1, 217, 47, 225, 182, 96, 99, 30, 104, 236, 234, 115, 212, 252, 199, 95, 96, 93, 62, 19, 150, 250, 91, 205, 227, 28, 59, 213, 166, 202, 118, 93, 162, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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: