Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bc619858df35b0efa957265cffb6bfdc253f5225f26dc6fbb4277fe15977344

Tx prefix hash: 5d7cf571052a4765367dd6bae8b0457ddf7e7a04697ef9d404c64ce6930b09c7
Tx public key: 9259988d6698c632071ce735c49db0f18ebd4fe12bf6a12e67a494dbd8f8c494
Timestamp: 1734752446 Timestamp [UTC]: 2024-12-21 03:40:46 Age [y:d:h:m:s]: 01:333:09:51:37
Block: 1179770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 502151 RingCT/type: yes/0
Extra: 019259988d6698c632071ce735c49db0f18ebd4fe12bf6a12e67a494dbd8f8c494021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2015c18e6e2e2871df2296160438890b85bde09f3bf53f9c3c2ae47ec12bf17 0.000600000000 1666169 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": 1179780, "vin": [ { "gen": { "height": 1179770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2015c18e6e2e2871df2296160438890b85bde09f3bf53f9c3c2ae47ec12bf17" } } ], "extra": [ 1, 146, 89, 152, 141, 102, 152, 198, 50, 7, 28, 231, 53, 196, 157, 176, 241, 142, 189, 79, 225, 43, 246, 161, 46, 103, 164, 148, 219, 216, 248, 196, 148, 2, 17, 0, 0, 0, 1, 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: