Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53e84657ebadc7b1b4b1dd9595ce8969cb80acd85b548d4cf8f6c5c811a58e1a

Tx prefix hash: 80054705214ea343283d14ae59e098a7fb7b71c6e6afa5f644d45e0d1a2f95b8
Tx public key: 25d511046d3485bce4d88cbb5aa4af514d4f99153392333abd8bd798b1a7a1a4
Timestamp: 1674984384 Timestamp [UTC]: 2023-01-29 09:26:24 Age [y:d:h:m:s]: 03:292:11:14:06
Block: 685225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 994664 RingCT/type: yes/0
Extra: 0125d511046d3485bce4d88cbb5aa4af514d4f99153392333abd8bd798b1a7a1a40211000000075029cbac000000000000000000

1 output(s) for total of 0.003292797774 xmr

stealth address amount amount idx tag
00: 1d3f463b385a4464071081d6644ee5b335550dd4c412e29c29e5867399b661b5 0.003292797774 1127518 of 0 -

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": 685235, "vin": [ { "gen": { "height": 685225 } } ], "vout": [ { "amount": 3292797774, "target": { "key": "1d3f463b385a4464071081d6644ee5b335550dd4c412e29c29e5867399b661b5" } } ], "extra": [ 1, 37, 213, 17, 4, 109, 52, 133, 188, 228, 216, 140, 187, 90, 164, 175, 81, 77, 79, 153, 21, 51, 146, 51, 58, 189, 139, 215, 152, 177, 167, 161, 164, 2, 17, 0, 0, 0, 7, 80, 41, 203, 172, 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: