Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 243fe8e85fbaff96faae08565e480dffe635ca475d5e50e9302dd925c5fe0600

Tx prefix hash: a44d241bd7e9ec24f5ec22823df02ad36d24db975a698751a70e0adb3896143d
Tx public key: b4d9cf5fe75808231e1a415f88a3db43e88a13223053103e2358f54b8fb8c5b2
Timestamp: 1730899316 Timestamp [UCT]: 2024-11-06 13:21:56 Age [y:d:h:m:s]: 00:151:22:09:17
Block: 1147834 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108404 RingCT/type: yes/0
Extra: 01b4d9cf5fe75808231e1a415f88a3db43e88a13223053103e2358f54b8fb8c5b2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad6df11b914fb47b54d43ef702c2b2f96081e2758309b3958792f2d28a22f357 0.600000000000 1632535 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": 1147844, "vin": [ { "gen": { "height": 1147834 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad6df11b914fb47b54d43ef702c2b2f96081e2758309b3958792f2d28a22f357" } } ], "extra": [ 1, 180, 217, 207, 95, 231, 88, 8, 35, 30, 26, 65, 95, 136, 163, 219, 67, 232, 138, 19, 34, 48, 83, 16, 62, 35, 88, 245, 75, 143, 184, 197, 178, 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