Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61a463ff8b7373449ac6dd8e3548378fcd2b54df674ce0680a2846e989c52296

Tx prefix hash: b855ba5e25ea4ba3989052edb91c5625e9a4561b36eec48917c6ca4e94c51aee
Tx public key: 3b2726edeeda289a499df614b4386e2e071f002ccf5440c91a7da85461b7d5ca
Timestamp: 1702129041 Timestamp [UCT]: 2023-12-09 13:37:21 Age [y:d:h:m:s]: 01:339:06:30:34
Block: 909387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 501356 RingCT/type: yes/0
Extra: 013b2726edeeda289a499df614b4386e2e071f002ccf5440c91a7da85461b7d5ca02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33217732fce8e6bd291f0a65f6c6acf449dc7839338f5b7e02a5f3818e2799df 0.600000000000 1366472 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": 909397, "vin": [ { "gen": { "height": 909387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33217732fce8e6bd291f0a65f6c6acf449dc7839338f5b7e02a5f3818e2799df" } } ], "extra": [ 1, 59, 39, 38, 237, 238, 218, 40, 154, 73, 157, 246, 20, 180, 56, 110, 46, 7, 31, 0, 44, 207, 84, 64, 201, 26, 125, 168, 84, 97, 183, 213, 202, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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