Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df784bb59088fb248665be50188f4bf0fcf83cad2d84b99b1b2f362a01d688db

Tx prefix hash: 6e5a977ea2168166afddebeabf3ba19b1109ff61b6cc47082e8636f7136a9665
Tx public key: a79cc3c14344e89d563a9766bab7b5f111f1dccef8728d207a932f25d6e75947
Timestamp: 1733716919 Timestamp [UCT]: 2024-12-09 04:01:59 Age [y:d:h:m:s]: 00:155:22:33:14
Block: 1171175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111266 RingCT/type: yes/0
Extra: 01a79cc3c14344e89d563a9766bab7b5f111f1dccef8728d207a932f25d6e75947021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25c0205274cfdd07eee5f898c1fc6c4601af0dbf63f9e6ea41f0dd502d3c4d8e 0.600000000000 1656914 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": 1171185, "vin": [ { "gen": { "height": 1171175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25c0205274cfdd07eee5f898c1fc6c4601af0dbf63f9e6ea41f0dd502d3c4d8e" } } ], "extra": [ 1, 167, 156, 195, 193, 67, 68, 232, 157, 86, 58, 151, 102, 186, 183, 181, 241, 17, 241, 220, 206, 248, 114, 141, 32, 122, 147, 47, 37, 214, 231, 89, 71, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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