Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24017e99893741f18e0b4860363814715d96720c38d6e65bef9f73cafb54324d

Tx prefix hash: f595c9829fe86682215ec629303a40fdb0e196c2097151582b0b3f7eca6d3252
Tx public key: 1c2876c6ece2a8aa75901b02b1056f164b903cf86b846596de17d0a13fb17ae6
Timestamp: 1705751893 Timestamp [UCT]: 2024-01-20 11:58:13 Age [y:d:h:m:s]: 01:066:01:25:39
Block: 939401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308305 RingCT/type: yes/0
Extra: 011c2876c6ece2a8aa75901b02b1056f164b903cf86b846596de17d0a13fb17ae60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7dfb15b3473883a213fcee91b1dad31b92af905e27204da9862acefd3fe15dff 0.600000000000 1397509 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": 939411, "vin": [ { "gen": { "height": 939401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7dfb15b3473883a213fcee91b1dad31b92af905e27204da9862acefd3fe15dff" } } ], "extra": [ 1, 28, 40, 118, 198, 236, 226, 168, 170, 117, 144, 27, 2, 177, 5, 111, 22, 75, 144, 60, 248, 107, 132, 101, 150, 222, 23, 208, 161, 63, 177, 122, 230, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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