Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: deea52f5749e45ca34983dad79a520f69c4959a0e7908b871ee37c92badcafbe

Tx prefix hash: 63424921010f6f1e3f022d4965bb8d155cf5a064553848cffabd3ffc0105bc6e
Tx public key: c1fcbbbfd5a4ff1f3d8b318d5857c6cf09b568e9ca2f6ac8d27940f794d231f4
Timestamp: 1725709313 Timestamp [UCT]: 2024-09-07 11:41:53 Age [y:d:h:m:s]: 00:124:17:39:33
Block: 1104894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89205 RingCT/type: yes/0
Extra: 01c1fcbbbfd5a4ff1f3d8b318d5857c6cf09b568e9ca2f6ac8d27940f794d231f4021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d5dbbcd0c2b6a739f63be1778ab4787d28990f27c774386058b55972281e99f 0.600000000000 1582209 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": 1104904, "vin": [ { "gen": { "height": 1104894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d5dbbcd0c2b6a739f63be1778ab4787d28990f27c774386058b55972281e99f" } } ], "extra": [ 1, 193, 252, 187, 191, 213, 164, 255, 31, 61, 139, 49, 141, 88, 87, 198, 207, 9, 181, 104, 233, 202, 47, 106, 200, 210, 121, 64, 247, 148, 210, 49, 244, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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