Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 862dc700a8fb6f20ba7f823b67e36970dd7a9af9d9039770919c37be1dfeab98

Tx prefix hash: 785157eeef38adb818459342e405d7452a95dbfe46470b9758b854de3b085bb3
Tx public key: a1b34088a56d6fce231ad67cd5d5cb1b793f2bd5052ba25f1c63571f87580a13
Timestamp: 1731976605 Timestamp [UCT]: 2024-11-19 00:36:45 Age [y:d:h:m:s]: 00:168:22:23:51
Block: 1156760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120567 RingCT/type: yes/0
Extra: 01a1b34088a56d6fce231ad67cd5d5cb1b793f2bd5052ba25f1c63571f87580a13021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bf8ced6b40cc483f2f63feaf07d5650ee8104273d2c5c1701bfe5efe3bfa33a 0.600000000000 1642383 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": 1156770, "vin": [ { "gen": { "height": 1156760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bf8ced6b40cc483f2f63feaf07d5650ee8104273d2c5c1701bfe5efe3bfa33a" } } ], "extra": [ 1, 161, 179, 64, 136, 165, 109, 111, 206, 35, 26, 214, 124, 213, 213, 203, 27, 121, 63, 43, 213, 5, 43, 162, 95, 28, 99, 87, 31, 135, 88, 10, 19, 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