Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 98395f5db926e23cb6180ff2dfe30516e8205ea0e51b9ebea7ff99824717f9bd

Tx prefix hash: 472453d144e06788851bf52d99d4af1e3de966c05e83fbf11beb5f8204174353
Tx public key: 056c8e82e944622205788cec19bd821d7ef86f63ee5a04c7a58aced784aecfb4
Timestamp: 1745206674 Timestamp [UTC]: 2025-04-21 03:37:54 Age [y:d:h:m:s]: 01:209:13:48:47
Block: 1266006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413785 RingCT/type: yes/0
Extra: 01056c8e82e944622205788cec19bd821d7ef86f63ee5a04c7a58aced784aecfb40211000000036c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0719778fbe5e82a48d7a297b08a4edd024533f222af4c30ab72277c3cbf6f286 0.000600000000 1753219 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": 1266016, "vin": [ { "gen": { "height": 1266006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0719778fbe5e82a48d7a297b08a4edd024533f222af4c30ab72277c3cbf6f286" } } ], "extra": [ 1, 5, 108, 142, 130, 233, 68, 98, 34, 5, 120, 140, 236, 25, 189, 130, 29, 126, 248, 111, 99, 238, 90, 4, 199, 165, 138, 206, 215, 132, 174, 207, 180, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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: