Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 479e690633dbe09e4e27efad487a2ae60708527c808cc2ad489475a9548cba73

Tx prefix hash: 58418ab968342b51e9c87907f1ad6d50c8485f92ae60adffbbce849a192b719d
Tx public key: 80aa4de291530be9e19062e0bda601d52f8e85b58c0bed1d4186d74833ae4a76
Timestamp: 1727070773 Timestamp [UCT]: 2024-09-23 05:52:53 Age [y:d:h:m:s]: 00:108:21:54:28
Block: 1116180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77864 RingCT/type: yes/0
Extra: 0180aa4de291530be9e19062e0bda601d52f8e85b58c0bed1d4186d74833ae4a7602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e71f0eda624b3c52f4b48fe5eceecaae4187f12cc4aeee428ca88755a7a7ac1e 0.600000000000 1596571 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": 1116190, "vin": [ { "gen": { "height": 1116180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e71f0eda624b3c52f4b48fe5eceecaae4187f12cc4aeee428ca88755a7a7ac1e" } } ], "extra": [ 1, 128, 170, 77, 226, 145, 83, 11, 233, 225, 144, 98, 224, 189, 166, 1, 213, 47, 142, 133, 181, 140, 11, 237, 29, 65, 134, 215, 72, 51, 174, 74, 118, 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