Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db05a83a9dda874a441e00d9bf07c856ea3b06fc4a6d079577705155266c5d8a

Tx prefix hash: badcd9226d53f9c77e75e0023661ac61166558e013839bf5a4351f59471798d3
Tx public key: 58d4026c57d74b2a04ed4e7104dce7dde2e890913c7b37ce3293ac5d763feebd
Timestamp: 1773509942 Timestamp [UTC]: 2026-03-14 17:39:02 Age [y:d:h:m:s]: 00:245:08:15:56
Block: 1497809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180743 RingCT/type: yes/0
Extra: 0158d4026c57d74b2a04ed4e7104dce7dde2e890913c7b37ce3293ac5d763feebd021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4381856496fabeba497a1114b16e6c0b5d08fa4c07366cae1c05beb76f617866 0.000600000000 1987451 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": 1497819, "vin": [ { "gen": { "height": 1497809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4381856496fabeba497a1114b16e6c0b5d08fa4c07366cae1c05beb76f617866" } } ], "extra": [ 1, 88, 212, 2, 108, 87, 215, 75, 42, 4, 237, 78, 113, 4, 220, 231, 221, 226, 232, 144, 145, 60, 123, 55, 206, 50, 147, 172, 93, 118, 63, 238, 189, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: