Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c6e794650bb4e16a2e95b70b4254d406afb44ee131ad0a28547d38e4d8805db

Tx prefix hash: a86075be595d51e6615e0f802e7d20479bcca068019ae6cff0c9615d19a375b1
Tx public key: 0fc7e108e93c66d9226cfa6c16b71cb20017fb1279068b668f6564d63e47f773
Timestamp: 1723896379 Timestamp [UCT]: 2024-08-17 12:06:19 Age [y:d:h:m:s]: 01:122:08:51:37
Block: 1089865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345959 RingCT/type: yes/0
Extra: 010fc7e108e93c66d9226cfa6c16b71cb20017fb1279068b668f6564d63e47f77302110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4502aae1901663b3acd9436062e38d8b54c529a2e5973f1bf856afd67505a7f1 0.600000000000 1564488 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 dinasty-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": 1089875, "vin": [ { "gen": { "height": 1089865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4502aae1901663b3acd9436062e38d8b54c529a2e5973f1bf856afd67505a7f1" } } ], "extra": [ 1, 15, 199, 225, 8, 233, 60, 102, 217, 34, 108, 250, 108, 22, 183, 28, 178, 0, 23, 251, 18, 121, 6, 139, 102, 143, 101, 100, 214, 62, 71, 247, 115, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8