Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 379b8b07f17c03bc2286deed48ed3e8204d5ce0ac3d367ac390acb3f70efb809

Tx prefix hash: 885d7c67dff5bc78eb52ca3cca9af1f7a07e2f1d42404b8aab542c7b0919e2f8
Tx public key: e591599451b2d8f6e6e585e6c4a7525909fb2c337ead59be67fc8e4259a387bc
Timestamp: 1723834289 Timestamp [UTC]: 2024-08-16 18:51:29 Age [y:d:h:m:s]: 02:092:05:58:53
Block: 1089342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590691 RingCT/type: yes/0
Extra: 01e591599451b2d8f6e6e585e6c4a7525909fb2c337ead59be67fc8e4259a387bc02110000000691e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 67bec4eae8ec4adf6434a2108a0b67f91b193e46a1d94d543633e9bb2b486d8e 0.000600000000 1563961 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": 1089352, "vin": [ { "gen": { "height": 1089342 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67bec4eae8ec4adf6434a2108a0b67f91b193e46a1d94d543633e9bb2b486d8e" } } ], "extra": [ 1, 229, 145, 89, 148, 81, 178, 216, 246, 230, 229, 133, 230, 196, 167, 82, 89, 9, 251, 44, 51, 126, 173, 89, 190, 103, 252, 142, 66, 89, 163, 135, 188, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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: