Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32ed943ae91c0f28745615905498e7699eb859610a91eab179b6eb6e37612361

Tx prefix hash: 14cc82612fc24655361d04ab7dddfcfb8687f2b1d5bc45169d50b43c225f14c9
Tx public key: 6f9d9f621ba11d9036dd2c7dcdf11d3b2d0cc88a0b01d24aa026817401c2d296
Timestamp: 1712377426 Timestamp [UCT]: 2024-04-06 04:23:46 Age [y:d:h:m:s]: 01:057:01:42:36
Block: 994322 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301830 RingCT/type: yes/0
Extra: 016f9d9f621ba11d9036dd2c7dcdf11d3b2d0cc88a0b01d24aa026817401c2d29602110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0be00f3cbcc75f520fa9a247bd233e04780d766de38f298c4d13b93e9f35bf0e 0.600000000000 1454724 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": 994332, "vin": [ { "gen": { "height": 994322 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0be00f3cbcc75f520fa9a247bd233e04780d766de38f298c4d13b93e9f35bf0e" } } ], "extra": [ 1, 111, 157, 159, 98, 27, 161, 29, 144, 54, 221, 44, 125, 205, 241, 29, 59, 45, 12, 200, 138, 11, 1, 210, 74, 160, 38, 129, 116, 1, 194, 210, 150, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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