Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 471d340b200a2498813ea4d7d7e9a025ecf14dee184c33651da3e71fa5cc6e24

Tx prefix hash: 92e7c9620f6112794780baa6592fea43c18276f77a01f25f129cd452b7f932bf
Tx public key: eeaf1391e91f5c9d6e5c650d46ba111947543ea197b15dc6906c468fa7d189be
Timestamp: 1774063097 Timestamp [UTC]: 2026-03-21 03:18:17 Age [y:d:h:m:s]: 00:239:14:17:54
Block: 1502358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176695 RingCT/type: yes/0
Extra: 01eeaf1391e91f5c9d6e5c650d46ba111947543ea197b15dc6906c468fa7d189be021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 371bd007c582ff1476d0ad0f51e497a1ce24e41d7a0504a237057e74eb8ccb6b 0.000600000000 1992056 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": 1502368, "vin": [ { "gen": { "height": 1502358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "371bd007c582ff1476d0ad0f51e497a1ce24e41d7a0504a237057e74eb8ccb6b" } } ], "extra": [ 1, 238, 175, 19, 145, 233, 31, 92, 157, 110, 92, 101, 13, 70, 186, 17, 25, 71, 84, 62, 161, 151, 177, 93, 198, 144, 108, 70, 143, 167, 209, 137, 190, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: