Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e6b4ce11fe897af32aa461001ae2a3784abfc95efd3aabee63b40b417437939

Tx prefix hash: 3710d4e30873c26722aa3276299b5d702dcfa0d4edf2a72c223b669190957860
Tx public key: 37902be7c5dd476187e144b7c0ba13813ece2b226605f346c9f8b5005c138307
Timestamp: 1578362869 Timestamp [UTC]: 2020-01-07 02:07:49 Age [y:d:h:m:s]: 06:262:05:04:11
Block: 40214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1602166 RingCT/type: yes/0
Extra: 0137902be7c5dd476187e144b7c0ba13813ece2b226605f346c9f8b5005c1383070211000000088a2ee0d9000000000000000000

1 output(s) for total of 0.451601287792 xmr

stealth address amount amount idx tag
00: 96f759544b5499a84fe36f65d0b79d418548534e52ed95fa1fbb349d93da7546 0.451601287792 70337 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": 40224, "vin": [ { "gen": { "height": 40214 } } ], "vout": [ { "amount": 451601287792, "target": { "key": "96f759544b5499a84fe36f65d0b79d418548534e52ed95fa1fbb349d93da7546" } } ], "extra": [ 1, 55, 144, 43, 231, 197, 221, 71, 97, 135, 225, 68, 183, 192, 186, 19, 129, 62, 206, 43, 34, 102, 5, 243, 70, 201, 248, 181, 0, 92, 19, 131, 7, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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: