Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe79ed4d169062f19f2ba811bb5cd6c5077443a7f10d566759cea3267d04a59d

Tx prefix hash: 6c8b852704b504016de39b36e67563188ebe5bfabed4ebf73535b7ea0e146648
Tx public key: cff3b54a16205bcdd8c4cb8e159cd4eb21298d942cf17e7e80881219edea21b2
Timestamp: 1578807660 Timestamp [UTC]: 2020-01-12 05:41:00 Age [y:d:h:m:s]: 06:121:03:36:16
Block: 43682 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1487847 RingCT/type: yes/0
Extra: 01cff3b54a16205bcdd8c4cb8e159cd4eb21298d942cf17e7e80881219edea21b202111ae5eee500000000000000000000000000

1 output(s) for total of 0.439809132368 xmr

stealth address amount amount idx tag
00: adb23881fe5a90af92f6e91aade28a36a7d24ca6dc3c356497945e05ab16159e 0.439809132368 79219 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": 43692, "vin": [ { "gen": { "height": 43682 } } ], "vout": [ { "amount": 439809132368, "target": { "key": "adb23881fe5a90af92f6e91aade28a36a7d24ca6dc3c356497945e05ab16159e" } } ], "extra": [ 1, 207, 243, 181, 74, 22, 32, 91, 205, 216, 196, 203, 142, 21, 156, 212, 235, 33, 41, 141, 148, 44, 241, 126, 126, 128, 136, 18, 25, 237, 234, 33, 178, 2, 17, 26, 229, 238, 229, 0, 0, 0, 0, 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: