Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db68a19b453ef20c1095d9d35e7d4678d7175453fad84198c8f6cb4d23498053

Tx prefix hash: df099e2f308c846351b2e5af59ae12d18ea5e14d4425cc356496f8ae9d05675f
Tx public key: 0cd58c34ec328ba7e0f40ad9f4369736117ffba198e07a1b3056b4f1781e07d2
Timestamp: 1719434974 Timestamp [UCT]: 2024-06-26 20:49:34 Age [y:d:h:m:s]: 00:263:14:27:25
Block: 1052866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188372 RingCT/type: yes/0
Extra: 010cd58c34ec328ba7e0f40ad9f4369736117ffba198e07a1b3056b4f1781e07d202110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b5e260a441efda01947ffe799f64d86c4b451fbb8e92baedb70ee29e3087545 0.600000000000 1523201 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": 1052876, "vin": [ { "gen": { "height": 1052866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b5e260a441efda01947ffe799f64d86c4b451fbb8e92baedb70ee29e3087545" } } ], "extra": [ 1, 12, 213, 140, 52, 236, 50, 139, 167, 224, 244, 10, 217, 244, 54, 151, 54, 17, 127, 251, 161, 152, 224, 122, 27, 48, 86, 180, 241, 120, 30, 7, 210, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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