Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b40ff3ecb9666e8791eab37a3720f9ee4e663beb0fd7f2c6e4403b7ccfa87038

Tx prefix hash: 4ca730569a5bc0db10016b98d11630163ced5d4f65402168cd3083aa3af0ca20
Tx public key: 4700084b64ba875203630433bffbcf68f158b7cf3d3e02c2c810d9d12e9ae7ff
Timestamp: 1705569478 Timestamp [UCT]: 2024-01-18 09:17:58 Age [y:d:h:m:s]: 01:040:01:23:54
Block: 937905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289685 RingCT/type: yes/0
Extra: 014700084b64ba875203630433bffbcf68f158b7cf3d3e02c2c810d9d12e9ae7ff02110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 680061acc2559c00831b07f5c5d9d9c2e567ce7ce7e718f997f433c658005ba2 0.600000000000 1395969 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": 937915, "vin": [ { "gen": { "height": 937905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "680061acc2559c00831b07f5c5d9d9c2e567ce7ce7e718f997f433c658005ba2" } } ], "extra": [ 1, 71, 0, 8, 75, 100, 186, 135, 82, 3, 99, 4, 51, 191, 251, 207, 104, 241, 88, 183, 207, 61, 62, 2, 194, 200, 16, 217, 209, 46, 154, 231, 255, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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