Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd388baf34adbb0ac8fd989ae5dc1ceca6a62f27aa6a298609b54c162679e2dc

Tx prefix hash: 87efe55f87324729b43f1d6890fa8d7441bc0261e04eea21c942e0e594a77c44
Tx public key: c902ed80d9d0ed6ca2bfbc9df973e4e6526af2947b093ad2c2b10963ec69e951
Timestamp: 1672050905 Timestamp [UTC]: 2022-12-26 10:35:05 Age [y:d:h:m:s]: 03:144:20:53:48
Block: 660914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 877191 RingCT/type: yes/0
Extra: 01c902ed80d9d0ed6ca2bfbc9df973e4e6526af2947b093ad2c2b10963ec69e951021100000001e7ace25d000000000000000000

1 output(s) for total of 0.003963852907 xmr

stealth address amount amount idx tag
00: 9b9b33658b85e3edd15de42a1db4a9c8b4d5ff7ed2f9bdb49edb927b87cf6767 0.003963852907 1101657 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": 660924, "vin": [ { "gen": { "height": 660914 } } ], "vout": [ { "amount": 3963852907, "target": { "key": "9b9b33658b85e3edd15de42a1db4a9c8b4d5ff7ed2f9bdb49edb927b87cf6767" } } ], "extra": [ 1, 201, 2, 237, 128, 217, 208, 237, 108, 162, 191, 188, 157, 249, 115, 228, 230, 82, 106, 242, 148, 123, 9, 58, 210, 194, 177, 9, 99, 236, 105, 233, 81, 2, 17, 0, 0, 0, 1, 231, 172, 226, 93, 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: