Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 319a6dd53b9d9dca84ac975e55844aa9d5335fc535f80904cfce87b0aca2539f

Tx prefix hash: d7143343dc5170399c87511414ec38b4332a4d4d9efaa04640a9c84925e90355
Tx public key: 92ea74c07524a5d606b9e94d6bbf47930aaa38233ad941507ee32ad9e61afb53
Timestamp: 1740124626 Timestamp [UTC]: 2025-02-21 07:57:06 Age [y:d:h:m:s]: 01:214:01:30:28
Block: 1223934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417785 RingCT/type: yes/0
Extra: 0192ea74c07524a5d606b9e94d6bbf47930aaa38233ad941507ee32ad9e61afb53021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 51ade3ffcf42197fe93ef78dc0949139cba0ed34a39db67f1340e2d9f7f0e4e6 0.000600000000 1710791 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": 1223944, "vin": [ { "gen": { "height": 1223934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51ade3ffcf42197fe93ef78dc0949139cba0ed34a39db67f1340e2d9f7f0e4e6" } } ], "extra": [ 1, 146, 234, 116, 192, 117, 36, 165, 214, 6, 185, 233, 77, 107, 191, 71, 147, 10, 170, 56, 35, 58, 217, 65, 80, 126, 227, 42, 217, 230, 26, 251, 83, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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: