Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 603f8d7821e27a92b22da0552b444c5c1246001f049a9db671ec35a417057a12

Tx prefix hash: ee2a8d12a20d0a95fe6845ba914e763f057bf1cbadf1011894ab41d6968c0210
Tx public key: 2fb1e4fd2e7f804d6f64d0df2be42d1ace016c601acf36e94de7fdcadf0c64e1
Timestamp: 1732356448 Timestamp [UCT]: 2024-11-23 10:07:28 Age [y:d:h:m:s]: 00:000:20:16:20
Block: 1159900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597 RingCT/type: yes/0
Extra: 012fb1e4fd2e7f804d6f64d0df2be42d1ace016c601acf36e94de7fdcadf0c64e1021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 641dc7b606b7161ea46aa4b129621f38aa97ce2575a51b67e75c580e00fad1d7 0.600000000000 1645539 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": 1159910, "vin": [ { "gen": { "height": 1159900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "641dc7b606b7161ea46aa4b129621f38aa97ce2575a51b67e75c580e00fad1d7" } } ], "extra": [ 1, 47, 177, 228, 253, 46, 127, 128, 77, 111, 100, 208, 223, 43, 228, 45, 26, 206, 1, 108, 96, 26, 207, 54, 233, 77, 231, 253, 202, 223, 12, 100, 225, 2, 17, 0, 0, 0, 2, 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