Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7cdbf521c63ded316c4278725aaba8d53b4fe8a09ca3430416eff6b81a5447c0

Tx prefix hash: c6f2e5f4766b6479b39de509fe6d82ff2e449e327249e3ca698fb23ec9dfcc54
Tx public key: 826382be9d1076eb1a08c13797f20f38d7a4e00f59e7c5768db65040a7c74aa2
Timestamp: 1673352485 Timestamp [UTC]: 2023-01-10 12:08:05 Age [y:d:h:m:s]: 03:316:11:45:18
Block: 671683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1011811 RingCT/type: yes/0
Extra: 01826382be9d1076eb1a08c13797f20f38d7a4e00f59e7c5768db65040a7c74aa20211000000015029cbac000000000000000000

1 output(s) for total of 0.003651197681 xmr

stealth address amount amount idx tag
00: 0c19b8c35f67577ad67c177ab083fde1a08b078efc224f551d6bfb34c6e70c8f 0.003651197681 1113180 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": 671693, "vin": [ { "gen": { "height": 671683 } } ], "vout": [ { "amount": 3651197681, "target": { "key": "0c19b8c35f67577ad67c177ab083fde1a08b078efc224f551d6bfb34c6e70c8f" } } ], "extra": [ 1, 130, 99, 130, 190, 157, 16, 118, 235, 26, 8, 193, 55, 151, 242, 15, 56, 215, 164, 224, 15, 89, 231, 197, 118, 141, 182, 80, 64, 167, 199, 74, 162, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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: